Adjust session provider early return logic #164
Conversation
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
|
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
What problem is this solving?
Adjusts the logic of the previous PR so as not to break VTEX "legacy" call center operator impersonation functionality.
In the B2B impersonation scenario, the session provider must validate that the user has a
storeUserEmailin their session -- in other words, they must be logged in to the storefront to be able to impersonate another B2B user.In the legacy impersonation scenario, the user must be accessing
account.myvtex.comas an admin user with the call center operator role, but not necessarily logged into the storefront. ThestoreUserEmailshould not be validated in this case.How should this be manually tested?
New version linked and tested in https://arthur--helmethouseprod.myvtex.com